Skip to content

feat(backend): add weighted fair job queue with priority scheduling#648

Merged
Smartdevs17 merged 5 commits into
Smartdevs17:mainfrom
od-hunter:feature/weighted-fair-job-queue
Jun 25, 2026
Merged

feat(backend): add weighted fair job queue with priority scheduling#648
Smartdevs17 merged 5 commits into
Smartdevs17:mainfrom
od-hunter:feature/weighted-fair-job-queue

Conversation

@od-hunter

Copy link
Copy Markdown
Contributor

Closes #597

Introduce WFQ scheduler across critical/high/normal/low priority classes,
BullMQ-backed persistence, billing job worker integration, and Prometheus
queue metrics to keep time-sensitive jobs ahead of analytics under load.
@drips-wave

drips-wave Bot commented Jun 24, 2026

Copy link
Copy Markdown

@od-hunter Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Integrate Smartdevs17/main into feature/weighted-fair-job-queue, keeping WFQ
queue infrastructure while adopting upstream MV refresh views and pg dependency.
@gitguardian

gitguardian Bot commented Jun 25, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
34266369 Triggered Generic Password e40c64a backend/config/tests/redis.test.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@Smartdevs17 Smartdevs17 merged commit daf4d68 into Smartdevs17:main Jun 25, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement background job queue priority scheduling with weighted fair queuing

2 participants